README.TXT NOTES ON MS-DOS VERSION 5.0 =========================== This readme provides important information not included in the Microsoft MS-DOS User's Guide and Reference or in online Help. Look through the following table of contents to determine whether your software or hardware is included. ATTENTION CODEVIEW AND INTEL ABOVEBOARD USERS +++++++++++++++++++++++++++++++++++++++++++++ APPNOTES.TXT contains critical information about using CodeView and Intel Aboveboard with MS-DOS 5.0. +++++++++++++++++++++++++++++++++++++++++++++ For information about using applications with MS-DOS 5.0, see the APPNOTES.TXT file. The following topics are discussed in this file: 1. Readme Conventions 2. Machine-Specific HIMEM.SYS Switches 3. Notes on Memory Management 3.1 Problems Loading into the Upper Memory Area 3.2 Intel Expanded-Memory Driver (EMM.SYS) 4. Notes on Windows 4.1 "High Memory Area in Use" Message (Windows/386 2.1) 4.2 "Cannot run Windows in standard mode" Message 5. Making Your Hardware Compatible with MS-DOS 5.0 5.1 XGA and EMM386.EXE 6. Making Your Network Compatible with MS-DOS 5.0 6.1 MS-DOS Shell and Networks 6.2 Novell Networks 6.3 PC-NFS 3.0 6.4 TOPS Network 6.5 IBM PC LAN 1.34 7. Documentation Corrections and Additions 7.1 New CV.COM for CodeView 7.2 Documentation Corrections 7.3 Hercules Display Adapter (MSHERC.COM) 7.4 QBasic "On Error" Command 1. README CONVENTIONS ===================== If you have questions about procedures or commands mentioned in this file, you will probably find answers in the Microsoft MS-DOS User's Guide and Reference. The following paragraphs describe frequently mentioned topics that the guide covers in more detail. Many sections of the readme discuss changing your CONFIG.SYS file. For detailed information about modifying a CONFIG.SYS file, see Chapter 11 of the MS-DOS User's Guide and Reference. The readme often refers to DEVICE commands in your CONFIG.SYS file. For example, one section recommends "adding a machine:1 switch to the DEVICE=HIMEM.SYS command in your CONFIG.SYS file." These DEVICE= statements indicate the type of command in the CONFIG.SYS file. You need to modify these statements to reflect the configuration of your system. For more information, see the DEVICE command in Chapter 14 of the MS-DOS User's Guide and Reference. The readme sometimes asks you to use the EXPAND command to copy files from the distribution disks to your hard disk. See Chapter 14 of the MS-DOS User's Guide and Reference for more information about using the EXPAND command. 2. MACHINE-SPECIFIC HIMEM.SYS SWITCHES -------------------------------------- This section contains HIMEM.SYS /machine switch values that are not included in the section "You receive the 'ERROR: Unable to control A20 line' message" in Chapter 3 of the Microsoft MS-DOS 5.0 Getting Started guide. Computer /machine value -------- -------------- Abacus 386 1 Chaplet 1 Everex AT Plus 1800 1 Everex Notebook ELX 1 Excel Computer Systems 13 OPT 386-25 motherboard 1 Pak 386SX 1 PC Limited 4 PC380/33C, PC350/33C, or PC 300/33C BIOS revision 1.14 2 3. NOTES ON MEMORY MANAGEMENT ============================= 3.1 Problems Loading into the Upper Memory Area ----------------------------------------------- Some computers with bus master DMA controllers may not be able to load device drivers or programs into the upper memory area. Try adding a DEVICE=SMARTDRV.SYS command before any DEVICEHIGH commands in your CONFIG.SYS file. 3.2 Intel Expanded-Memory Driver (EMM.SYS) ------------------------------------------ If you use Intel's EMM.SYS driver with Aboveboard, use EMM.SYS version 4.0 revision D or later. If you have an earlier version, contact Intel for a free upgrade. 4. NOTES ON WINDOWS =================== 4.1 "High Memory Area in Use" Message (Windows/386 2.1) ------------------------------------------------------- You cannot run Windows/386 2.1 when MS-DOS 5.0 is loaded into the high memory area. Also, the MS-DOS 5.0 versions of SMARTDRV.SYS and RAMDRIVE.SYS are not compatible with Windows/386 2.1. To run Windows/386 2.1 with MS-DOS 5.0, use the versions of SMARTDRV.SYS and RAMDRIVE.SYS that came with Windows and remove the DOS=HIGH command, if any, from your CONFIG.SYS file. 4.2 "Cannot run Windows in standard mode" Message ------------------------------------------------- If you have a DEVICE=EMM386.EXE command that includes the RAM or NOEMS switch in your CONFIG.SYS file, you cannot run Windows 3.0 in standard mode. Either remove the RAM or NOEMS switch or run Windows in real or enhanced mode. (If you remove RAM or NOEMS, you won't be able to load programs and device drivers into the upper memory area. If you include RAM or NOEMS, you won't be able to run Windows in standard mode.) NOTE: Using EMM386 may reduce the amount of extended memory available to Windows and cause Windows to try to start in standard mode. To prevent this, reduce the amount of extended memory that other device drivers use. For example, if you are using SMARTDrive, try setting the MinCacheSize parameter to 0. 5. MAKING YOUR HARDWARE COMPATIBLE WITH MS-DOS 5.0 ================================================== 5.1 XGA and EMM386.EXE ---------------------- If you use an XGA display with EMM386.EXE, you may need to exclude certain memory ranges with the EMM386 EXCLUDE option (x=). To determine which memory ranges to exclude, use your reference disk to view the memory map. 6. MAKING YOUR NETWORK COMPATIBLE WITH MS-DOS 5.0 ================================================= 6.1 MS-DOS Shell and Networks ----------------------------- Most network software won't work correctly if you start it from a MS-DOS Shell command prompt. Start your network before starting MS-DOS Shell. 6.2 Novell Networks ------------------- Novell Remote Workstations (RPLFIX.COM): If you can't load MS-DOS 5.0 on your remote-boot workstation, contact Novell for the RPLFIX.COM file. Drive Mapping Utilities: If you run LOGIN.EXE, MAP.EXE, and SESSION.EXE from MS- DOS Shell or while MS-DOS Shell is running, a search path is not added to the existing path. Use these programs before starting MS-DOS Shell. COMSPEC Variable: If you use the Novell login program to set the COMSPEC variable after starting MS-DOS 5.0, and you can't reload the COMMAND.COM file, edit the SHELL command line in your CONFIG.SYS file. Make sure the path to COMMAND.COM points to the root directory and remove the c:\dos\ parameter that follows the path, if one exists. For example, suppose your SHELL command line looks like this: SHELL=C:\DOS\COMMAND.COM C:\DOS\ /P /E:512 Change it to look like this: SHELL=C:\COMMAND.COM /P /E:512 Or contact your Novell vendor to get a new login program. 6.3 PC-NFS 3.0 -------------- If you use PC-NFS 3.0 with MS-DOS Shell, MS-DOS Shell may display more drives than you have currently enabled. To prevent this, use the PC-NFS /d switch to specify the number of drives you are using. For more information, see your PC- NFS documentation. If you can't use the COPY or XCOPY command on PC-NFS 3.01, contact your vendor to get an updated version of the PCNFS.SYS device driver. 6.4 TOPS Network ---------------- If your system is a TOPS workstation, the MS-DOS Shell MOVE command may not work. Don't use the LOADHIGH command with a TOPS network. 6.5 IBM PC LAN 1.34 ------------------- If you have problems with applications that use record locking or file locking, you may need an updated REDIR50.EXE file included in ICO 3039. Contact IBM Support Channel. 7. DOCUMENTATION CORRECTIONS AND ADDITIONS ========================================== 7.1 New CV.COM for CodeView --------------------------- Users of CodeView versions 3.0 to 3.13 should use the program CV.COM to start CodeView. For more details, see the section on CodeView in the file APPNOTES.TXT. 7.2 Documentation Corrections ----------------------------- The following is a correction to the Microsoft MS-DOS Getting Started manual: Page 24 (steps 6 and 7 of the procedure): To determine whether you have the correct version of EMM386.EXE, disregard the file dates (as stated in steps 6 and 7 of the procedure). Instead, to check which version of EMM386 you are using: 1. Quit Windows, if you are using it. 2. Type EMM386 at the command prompt. MS-DOS displays the version of EMM386 you are using. 3. If the message indicates you are using version 4.33 or later, you are using the correct version. If you are using a version earlier than 4.33, expand and copy the newer version included with MS-DOS 5.0 by following step 7 of the procedure in Getting Started. Page 32 (Lotus 1-2-3 version 3.1 won't start) The information in this section also applies to Lotus 1-2-3 version 3.0. The following are corrections to the Microsoft MS-DOS User's Guide and Reference: FORMAT Command: If you can't use the FORMAT command to format an unformatted disk, try using the /u switch. MIRROR Command: You cannot use the MIRROR command with a network drive or any drive you created by using the ASSIGN, SUBST, or JOIN command. UNDELETE Command: Do not use the UNDELETE command in the following circumstances: * When other programs are active. * With the LOAD= command or the Shift+Enter key combination in Windows or MS-DOS Shell. * With Task Swapper in MS-DOS Shell. UNFORMAT Command: The UNFORMAT /p switch is not compatible with the /j switch. RAMDRIVE.SYS Device Driver: Valid values for the RAMDrive DiskSize parameter are 4 through 32767. The following is a correction to the command-line Help: COMP /? Help: Online help for the COMP command /d switch should state that the default format is hexadecimal. 7.3 Hercules Display Adapter (MSHERC.COM) ----------------------------------------- If you use MS-DOS Editor or QBasic with a Hercules display adapter, run MSHERC.COM before you run either program. 7.4 QBasic "On Error" Command ----------------------------- Online help for Microsoft QBasic incorrectly states that ON ERROR RESUME NEXT is a valid statement. The correct syntax is as follows: ON ERROR GOTO